Skip to content

chore: update tools.json#5159

Open
asyncapi-bot wants to merge 9 commits intomasterfrom
update-tools/regenerateTools
Open

chore: update tools.json#5159
asyncapi-bot wants to merge 9 commits intomasterfrom
update-tools/regenerateTools

Conversation

@asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Feb 16, 2026

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • Updates
    • Tool catalog reorganized with updated metadata, classifications, and ownership indicators across multiple categories
    • Documentation and repository links corrected for improved accuracy
    • Language and technology tag organization updated

@netlify
Copy link

netlify bot commented Feb 16, 2026

Deploy Preview for asyncapi-website failed.

Name Link
🔨 Latest commit 0ccbf57
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/69953b6257f9a80007a45a2d

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 16, 2026

📝 Walkthrough

Walkthrough

Three configuration files were updated with metadata modifications: catalog tag names swapped in all-tags.json, extensive tool entries reorganized and reclassified in tools-automated.json with category and ownership adjustments, and repository and documentation URLs corrected in tools.json.

Changes

Cohort / File(s) Summary
Metadata Tag Swaps
config/all-tags.json
Two paired name swaps: "Django" ↔ "ASP.NET Core" in languages array, and "SmartPaste" ↔ "JetBrains" in technologies array.
Tool Catalog Reorganization
config/tools-automated.json
Extensive reclassification of tool entries across categories (Code-first, DSL, Mocking and Testing, Generators, Validators, IDE Extensions, etc.) with updated titles, descriptions, language/technology filters, categories, ownership flags, and repository/documentation links.
URL Corrections
config/tools.json
Two repository URL swaps for Editor entries and two documentation path corrections for Mokapi entries from /docs/guides/welcome to /docs/welcome.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Poem

A hop through catalogs both old and new,
Tags swap and shuffle—what a debut! 🐰
Tools rearranged from left to right,
URLs fixed, configurations bright,
The warren's toolkit shines today!

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title only references tools.json, but the changeset modifies three files: all-tags.json, tools-automated.json, and tools.json. Update the title to reflect all modified files or use a more descriptive title like 'chore: update tools and tags configuration' to accurately represent the full scope of changes.
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into master

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch update-tools/regenerateTools

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov
Copy link

codecov bot commented Feb 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (881a1a5) to head (0ccbf57).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #5159   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          796       796           
  Branches       146       146           
=========================================
  Hits           796       796           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@config/tools-automated.json`:
- Around line 118-136: The "language" value for the JSON entry titled
"nestjs-asyncapi" is spelled "Typescript" and must be normalized to "TypeScript"
to match the rest of the file; locate the object with "title": "nestjs-asyncapi"
and update its "language" property to "TypeScript" so case-sensitive consumers
and filters behave consistently.
- Around line 594-615: The "Specmatic" entry's filters.technology contains
"maven" in lowercase which is inconsistent with the rest of the catalog; update
the value in the Specmatic object (the "title": "Specmatic") by changing the
"maven" string to "Maven", and make the same change for the other CLIs entry
that uses "maven" so all filters.technology values use the capitalized "Maven"
consistently.

Comment on lines +118 to +136
{
"title": "nestjs-asyncapi",
"description": "Utilize decorators to generate AsyncAPI document utilizing DTOs (similar to @nestjs/swagger) and a web UI.",
"links": {
"repoUrl": "https://github.com/flamewow/nestjs-asyncapi"
},
"filters": {
"language": "Typescript",
"technology": [
"Node.js",
"NestJS"
],
"categories": [
"code-first"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Inconsistent casing: "Typescript" vs "TypeScript" on line 125.

The nestjs-asyncapi entry uses "language": "Typescript" (lowercase 's') while other entries in this file consistently use "TypeScript" (e.g., line 40, 235, 509). This could cause filtering/matching issues if consumers do case-sensitive comparisons.

Proposed fix
        "filters": {
-          "language": "Typescript",
+          "language": "TypeScript",
          "technology": [
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
{
"title": "nestjs-asyncapi",
"description": "Utilize decorators to generate AsyncAPI document utilizing DTOs (similar to @nestjs/swagger) and a web UI.",
"links": {
"repoUrl": "https://github.com/flamewow/nestjs-asyncapi"
},
"filters": {
"language": "Typescript",
"technology": [
"Node.js",
"NestJS"
],
"categories": [
"code-first"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
},
{
"title": "nestjs-asyncapi",
"description": "Utilize decorators to generate AsyncAPI document utilizing DTOs (similar to `@nestjs/swagger`) and a web UI.",
"links": {
"repoUrl": "https://github.com/flamewow/nestjs-asyncapi"
},
"filters": {
"language": "TypeScript",
"technology": [
"Node.js",
"NestJS"
],
"categories": [
"code-first"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
},
🤖 Prompt for AI Agents
In `@config/tools-automated.json` around lines 118 - 136, The "language" value for
the JSON entry titled "nestjs-asyncapi" is spelled "Typescript" and must be
normalized to "TypeScript" to match the rest of the file; locate the object with
"title": "nestjs-asyncapi" and update its "language" property to "TypeScript" so
case-sensitive consumers and filters behave consistently.

Comment on lines +594 to +615
{
"title": "Specmatic",
"description": "Transform your API Specs into Executable Contracts with #NoCode in Seconds. Experience the power of Contract-Driven Development to confidently develop and independently deploy your Microservices and Microfrontends faster",
"links": {
"websiteUrl": "https://specmatic.io",
"docsUrl": "https://specmatic.io/documentation/",
"repoUrl": "https://github.com/specmatic/specmatic"
},
"filters": {
"language": "kotlin",
"technology": [
"Docker",
"maven"
],
"categories": [
"mocking-and-testing",
"CLIs"
],
"hasCommercial": true,
"isAsyncAPIOwner": false
}
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Inconsistent technology tag casing: "maven" (lowercase) on line 606.

The Specmatic entry uses "maven" (lowercase) while other entries consistently use "Maven" with a capital M (e.g., lines 211, 627, 832). Same issue appears in the CLIs section at line 792. This could cause filtering mismatches.

Proposed fix
          "technology": [
            "Docker",
-            "maven"
+            "Maven"
          ],

Apply in both locations (line 606 and line 792).

🤖 Prompt for AI Agents
In `@config/tools-automated.json` around lines 594 - 615, The "Specmatic" entry's
filters.technology contains "maven" in lowercase which is inconsistent with the
rest of the catalog; update the value in the Specmatic object (the "title":
"Specmatic") by changing the "maven" string to "Maven", and make the same change
for the other CLIs entry that uses "maven" so all filters.technology values use
the capitalized "Maven" consistently.

@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: To Be Triaged

Development

Successfully merging this pull request may close these issues.

2 participants